Fix compatibility with page and app router #87
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses two issues:
Compatibility with next/dist imports: In certain applications, the SDK could not import classes from next/dist. To resolve this, the logic has been moved directly into the SDK.
Hook compatibility with App Router: The hook was failing when used with the App Router because it was relying on the useRouter implementation compatible only with the Page Router. This has been updated to properly check and ensure compatibility, preventing errors.
Checklist